27 research outputs found

    A practical approach to multi-modeling views composition

    Get PDF
    The use of several view models to specify a complex system is a common practice to provide the most appropriate abstractions to model its diverse concerns. When several view models are used to specify a system, it is necessary to compose them to generate the application. When the view models are expressed in different Domain Specific Modeling Languages a problem arises because a heterogeneous composition is required. A possible approach to avoid a heterogeneous composition is to transform the diverse models into low-level models using a common low-level modeling language as target. Therefore, when all the view models are transformed in low-level models specified with a common language, it is possible to apply a ho- mogeneous composition to obtain the final application. However, it is necessary to identify the elements to compose in the low-level. In this paper, we present an auto- matic mechanism to identify which elements will be composed. This mechanism is based on defining correspondence relationships between the high-level view mod- els and automatically deriving new correspondence between the generated low-level models

    Towards Multi-View Feature-based Configuration

    Get PDF
    Abstract. [Context & motivation] Variability models, feature diagrams ahead, have become commonplace in software product line engineering as a means to document variability early in the lifecycle. Over the years though, their appli-cation span has been extended to aid stakeholders in the configuration of soft-ware products. [Question/problem] However, current feature-based configura-tion techniques hardly support the tailoring of configuration views to the profiles of heterogeneous stakeholders. [Principal ideas/results] In this paper, we intro-duce a lightweight mechanism to leverage multidimensional separation of con-cerns in feature-based configuration. [Contribution] We propose a technique to specify concerns in feature diagrams and to build automatically concern-specific configuration views, which come with three alternative visualisations.

    A Declarative DSL Approach to UI Specification - Making UI's Programming Language Independent

    No full text
    Introduction The problem of separation of concerns exists in many flavours and is widely acknowledged in the software development community [HL95]. Currently a large number of researchers are trying to find innovative ways to tackle this problem. The most well-known research fields that focus on this are aspect-oriented programming [KLM 97], component based programming [Szy98], ... The techniques proposed by these researchers depend on the type of concern they focus on (examples of this are transaction management, logging, synchronization, ...). In our research we focus on the concern of User Interfaces and application interactions. In practice the user interface concerns are seldom separated from the application concerns. A clean separation would nevertheless facilitate UI development and evolution. Nowadays the UI representation (i.e. drawing windows, text-boxes, buttons, ... ) can easily be separated from everything else. After drawing the UI, in general some stubs are generat
    corecore